Query Failure #6947
Open
Query Failure #6947
+134
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9 tasks
stephanos
approved these changes
Dec 6, 2024
| // Abort and fail the test. | ||
| s.NoError(ctx.Err()) | ||
| } | ||
|
|
There was a problem hiding this comment.
Could you add a small comment explaining the purpose of the second half of the test? I don't quite see the difference to the first half.
ychebotarev
approved these changes
Dec 6, 2024
ychebotarev
approved these changes
Dec 6, 2024
| s.Equal("my error message", query1FailedErr.Message) | ||
| s.Equal("my failure error message", query1FailedErr.Failure.Message) | ||
|
|
||
| go func() { |
There was a problem hiding this comment.
q: why not just a single test, with both "QueryWorkflow" and "PollWorkflowTaskQueue/RespondQueryTaskCompleted" in a separate goroutines? What are you testing by testing like that?
bergundy
commented
Dec 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Attach a Failure object from query failures to the QueryFailure serviceerror.
Why?
Allows encryption of failure messages and stack traces.
See also temporalio/api/pull/503.